1 link tagged with all of: mcp + chatgpt apps + opus 5.5 + dots
Click any tag below to further narrow down your results
Links
@vartekxx on X
This is a how-to guide for connecting Anthropic's Opus 5.5 model to a Dots (ChatGPT-based) team as an external tool, so the orchestrating dot can hand off deep research, stricter reviews, chart reading, and long-running batch work. The author argues Dots stays fast but skims complex sources, uses flat effort, and reviews weakly.
- The bridge is a single private tool, run_opus_task, built with the Apps SDK or MCP, with the Anthropic key kept on a backend the user controls and read-only access to start.
- Reviews should come from a separate run that does not produce the work, with a strict JSON schema (additionalProperties: false) so every failure needs evidence and unverifiable claims must be declared.
- Cost savings come from prompt caching: put the unchanging material first, add a breakpoint, and rely on the one-hour TTL so a team's morning, midday, and lunchtime runs share one cache write.